-- card: 10520 from stack: in
-- bmap block id: 0
-- flags: 0000
-- background id: 2619
-- name: CALCULATED NAVIGATION


-- part 1 (field)
-- low flags: 01
-- high flags: 0001
-- rect: left=37 top=42 right=91 bottom=475
-- title width / last selected line: 0
-- icon id / first selected line: 0 / 0
-- text alignment: 1
-- font id: 3
-- text size: 12
-- style flags: 8448
-- line height: 16
-- part name: 


-- part contents for card part 1
----- text -----
Commands and Structures to Avoid

CALCULATED NAVIGATION


-- part contents for background part 2
----- text -----

Because HyperDA does not support mathematical operations or date arithmetic, you should avoid designing handlers that depend on such calculations to determine where to go in response to a user’s navigation command.  For example, if you were designing an appointment-tracking stack, you might have a button that moves the user forward in the stack by seven cards when he indicates he wants to advance one week from the currently visible card.  Rather than using date arithmetic to calculate the date of the destination card (which would work fine in HyperCard), you might try  seven go to next card  statements.  (Notice that it is not legal to use the repeat approach that might first come to mind because HyperDA does not support this command.)